The bl_tempload examples in the SAS Anti-Money Laundering System Administration Guide contain incorrect syntax. As shown below, the bulkload options are separated by commas:
bl_tempload=%str(bulkload=yes, bl_load_method=truncate,
bl_log=&AMLROOT/logs/get_entity_info.log));
The commas cause a Too many parameters error to the INDEX function (for example, when running the %riskranking macro):
ERROR: Macro function %INDEX has too many arguments. The excess arguments will be ignored.
BULKLOADTEMP VERSION 4.1
ERROR: AML: RISKRANKING: bl_tempload parameters do not include bl_load_method=truncate
There are two locations in the System Administration Guide documentation where the
commas need to be removed (the riskranking and get_entity_info documentation):
p. 37 - 5.2.4.5 Example:
%riskranking (inLib=stg_aler,
inDS=combined_alerts,
inRiskLib=stg_aler,
inRiskDS=risk_factor_alerts,
outLib=stg_aler,
outDS=ranked_alerts,
outRiskLib=mst_aler,
outRiskDS=ranked_risk_factor_alerts,
riskonly=Y,
bl_temp=YES,
bl_tempload=%str(bulkload=yes,
bl_load_method=truncate,
bl_log=&AMLROOT/logs/replicateTransactions.log));
p. 43 5.2.6.5 Example:
%get_entity_info(inLib=STG_ALER,
inDS=ranked_alerts,
outLib=STG_ALER,
outDS=entity_alerts,
bl_temp=Yes
bl_tempload=%str(bulkload=yes, bl_load_method=truncate,
bl_log=&AMLROOT/logs/get_entity_info.log));
The correct syntax is shown below (note the removal of the commas in the %str parameter):
bl_tempload=%str(bulkload=yes
bl_load_method=truncate
bl_log="&AMLROOT/logs/replicateTransactions.log"));
Operating System and Release Information
SAS System | SAS Anti-Money Laundering | Solaris for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Linux for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Linux | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
HP-UX IPF | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
64-bit Enabled Solaris | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
64-bit Enabled HP-UX | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
64-bit Enabled AIX | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Windows Vista for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Windows Vista | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Windows 7 Ultimate x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Windows 7 Ultimate 32 bit | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Windows 7 Professional x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Windows 7 Professional 32 bit | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Windows 7 Home Premium x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Windows 7 Home Premium 32 bit | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Windows 7 Enterprise x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Windows 7 Enterprise 32 bit | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows XP Professional | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2008 for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2008 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Standard Edition | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Enterprise Edition | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Datacenter Edition | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft® Windows® for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.